Skip to content

appInfoViewer: Wrap Identifier and Runtime instead of ellipsizing - #895

Open
Malika7188 wants to merge 3 commits into
tchx84:masterfrom
Malika7188:fix/runtime-wrap
Open

Malika7188 wants to merge 3 commits into
tchx84:masterfrom
Malika7188:fix/runtime-wrap

Conversation

@Malika7188

Copy link
Copy Markdown
Contributor

The Runtime and Identifier values could get cut off with "…" and stay
that way regardless of window size, since the column they sit in has
a fixed width. Wrapping instead of ellipsizing means the full value is
always visible.

Verified in a real build, in English and in Indonesian (a language
with noticeably longer translated labels), at several window widths
including the single-pane layout.

Closes #792

Both fields could get cut off with no way to see the full value, even
after resizing the window wider, since the space given to them stays
fixed either way.

Closes tchx84#792

@tchx84 tchx84 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @Malika7188 , I tested this but, by switching to a GtkBox, it breaks completely the alignment between between fields and values. See image below:

Image

Please check if there's a way to preserve the alignment, or to fix this within the original container.

Both fields could get cut off with no way to see the full value, even
after resizing the window wider, since the space given to them stays
fixed either way.

Keeping the descriptions and the values in two separate containers only
worked while every row was one line tall. Move both into a single grid,
so each description shares a row with its value and stays with it when
the value wraps.

Closes tchx84#792
@Malika7188

Copy link
Copy Markdown
Contributor Author

Hi @tchx84 , I fixed the alignment. The descriptions and the values were in two separate containers, so I moved them into one grid where each description shares a row with its value. I tested this at different window sizes in English
and Indonesian.

While testing, I also noticed the dates are not formatted correctly in Indonesian when the day is a single digit. See the screenshot below:

Screenshot From 2026-10-02 02-01-16

@tchx84

tchx84 commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Hi @tchx84 , I fixed the alignment. The descriptions and the values were in two separate containers, so I moved them into one grid where each description shares a row with its value. I tested this at different window sizes in English and Indonesian.

This fixed the alignment but introduces a new issue / visual artifact:

Screenshot From 2026-10-02 12-01-45

Note that contents of the panel gets occluded when resizing the screen, accompanied with the following warning:

(com.github.tchx84.Flatseal:2): Adwaita-WARNING **: 12:01:37.968: AdwNavigationSplitView 0x56292721dc90 exceeds FlatsealWindow width: requested 614 px, 564 px available

This consistently happens in this branch, but doesn't in the original. Can you investigate?

Both fields could get cut off with no way to see the full value, even
after resizing the window wider, since the space given to them stays
fixed either way.

A wrapped value needs its description to grow along with it, which the
two separate containers cannot do. The fix pair each description with
its value in a row of its own, and keeps the descriptions a single width
with a size group.

Closes tchx84#792
@Malika7188

Copy link
Copy Markdown
Contributor Author

This consistently happens in this branch, but doesn't in the original. Can you investigate?

Hi @tchx84 , you were right, it came from my change. I had set a minimum width on the wrapping labels, which raised the minimum width of the whole panel.

I have fixed that and now pair each description with its value in a row of its own, with a size group keeping the descriptions a consistent width. This removes the need for the minimum width, and the panel now requests the same minimum as master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make "Runtime" field value wraparound

2 participants